On 3/10/2024 11:48 AM, Wolfgang Schuster wrote:
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
Hans Hagen via ntg-context schrieb am 10.03.2024 um 10:46:
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to
On 3/10/24 10:46, Hans Hagen via ntg-context wrote:
> [...]
> using the low level commands
>
> \glyphscale
> \glyphxscale
> \glyphyscale
> \glyphslant
> \glyphweight
>
> directly can have side efects when at an outer level these are also set,
> so you need to accumulate, like
> [...]
> which you
On 3/10/2024 9:32 AM, Pablo Rodriguez via ntg-context wrote:
On 3/9/24 16:04, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
[...]
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by
On 3/9/24 16:04, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
>> [...]
>>\enableexperiments[fonts.compact]
>>
>> Which seeems weird to me. Or at least, I thought I read that Hans
>> enabled it by default in LMTX.
>
> AFAIR Hans uses the setting in
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected output.
Sorry, my LuaTeX is getting
Am 08.03.24 um 18:50 schrieb Pablo Rodriguez via ntg-context:
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality},
it={style: regular, features:{default, quality, slanted}},
sl={style
On 3/30/2023 6:22 PM, Thomas A. Schmitz via ntg-context wrote:
Hi all,
I wanted to use a rightbrace as background for a table, as defined in
meta-imp-fen.mkiv. Unfortunately, I can't get it to work, for 2 reasons:
1. meta-imp-fen doesn't appear to be ported to mkxl.
2. When I try to compile
Hi all,
I wanted to use a rightbrace as background for a table, as defined in
meta-imp-fen.mkiv. Unfortunately, I can't get it to work, for 2 reasons:
1. meta-imp-fen doesn't appear to be ported to mkxl.
2. When I try to compile with the --luatex switch, I get this error message:
tex error
On 2/17/2020 10:56 PM, Pablo Rodriguez wrote:
On 2/17/20 7:49 PM, Hans Hagen wrote:
On 2/17/2020 4:51 PM, Pablo Rodriguez wrote:
[...]
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the same output in both MkIV and MkXL. The real
problem
On 2/17/20 7:49 PM, Hans Hagen wrote:
> On 2/17/2020 4:51 PM, Pablo Rodriguez wrote:
>> [...]
>> Sorry if I hadn’t expressed myself accurately before. The issue here
>> isn’t having exactly the same output in both MkIV and MkXL. The real
>> problem is that characters ar
t make any difference with TeX Gyre
Heros (https://pdf.ousia.tk/stretch-mkxl-hz.pdf) and it only corrected
one problematic case with Source Serif Pro
(https://pdf.ousia.tk/stretch-ssp-mkxl-hz.pdf).
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the same outp
n’t make any difference with TeX Gyre
Heros (https://pdf.ousia.tk/stretch-mkxl-hz.pdf) and it only corrected
one problematic case with Source Serif Pro
(https://pdf.ousia.tk/stretch-ssp-mkxl-hz.pdf).
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the
, hz]
\setupbodyfont[mainface, 17pt]
%~ \setupbodyfont[helvetica, 17pt]
\starttext
\input zapf
\stoptext
hz doesn’t work fine in MkXL, but it works fine in MkIV.
I think the flow of characters is broken in MKXL. Some
With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf
]
%~ \setupbodyfont[helvetica, 17pt]
\starttext
\input zapf
\stoptext
hz doesn’t work fine in MkXL, but it works fine in MkIV.
I think the flow of characters is broken in MKXL. Some
With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf and
https://pdf.ousia.tk/mkxl-hz.pdf):
- "computer&quo
18 matches
Mail list logo
